Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1221

reference
460-tree-1
name
1221
tree-preservation-order

undefined

460-tpo-1
uprn
address-text
point
POINT (-1.024148 50.884221)
geometry
MULTIPOLYGON (((-1.024034 50.884209,-1.024039 50.884231,-1.024055 50.884251,-1.024080 50.884267,-1.024111 50.884278,-1.024146 50.884282,-1.024182 50.884278,-1.024214 50.884268,-1.024239 50.884253,-1.024256 50.884233,-1.024262 50.884211,-1.024257 50.884188,-1.024241 50.884168,-1.024216 50.884152,-1.024185 50.884142,-1.024149 50.884138,-1.024114 50.884141,-1.024082 50.884151,-1.024057 50.884167,-1.024040 50.884187,-1.024034 50.884209)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL